Providing storage resources from a storage pool

ABSTRACT

Locally providing cloud storage array services for a plurality of storage systems within a data center by: receiving a request for storage resources from an operating system level virtualization service; determining, among the plurality of storage systems; an implementation of the request from the operating system level virtualization service; and providing storage resources to the operating system level virtualization service in accordance with the implementation of the request from the operating system level virtualization service.

CROSS-REFERENCE TO RELATED APPLICATIONS

This is a continuation application for patent entitled to a filing dateand claiming the benefit of U.S. patent application Ser. No. 16/254,859,filed Jan. 23, 2019, which is a continuation in part of and claimspriority from U.S. Pat. No. 10,652,331, issued May 12, 2020, which is acontinuation application of and claims priority from U.S. Pat. No.10,027,757, issued Jul. 17, 2018, which is a continuation application ofand claims priority from U.S. Pat. No. 9,716,755, issued Jul. 25, 2017.

BACKGROUND Field of Technology

The field of technology is data processing, or, more specifically,methods, apparatus, and products for providing cloud storage arrayservices for a storage array of a data center when the storage array isnot connected to a remote cloud-based storage array services provider.

Description of Related Art

Data centers may include many computing components including servers,network devices, and storage arrays. As the need for storage of largeamounts of data and efficient access to that data increases, storagearray technology is advancing. Such storage arrays may providepersistent storage for any number of computing devices in a data center.Given that many data centers provide services to many different users,various considerations must be taken into account to provide efficient,useful, and secure access to and administration of storage arrays.Various management tools, reporting services, and the like may beimplemented for storage array through cloud-based service providers. Insome implementations, however, such cloud-based service providers may beunavailable, either by design or through a loss of connection.

SUMMARY

Methods, apparatus, and products for locally providing cloud storagearray services for a storage array of a data center when the storagearray is not connected to a remote cloud-based storage array servicesprovider are disclosed in this specification. Providing such cloudstorage array services in accordance with embodiments of the presentinvention includes: initiating, by a primary storage array, one or morecloud storage array services; and locally providing the cloud storagearray services including: generating, by the cloud storage arrayservices, metadata describing one or more real-time storage arraycharacteristics; and presenting the metadata to a user through a localarea network.

The foregoing and other objects, features and advantages of theinvention will be apparent from the following more particulardescriptions of exemplary embodiments of the invention as illustrated inthe accompanying drawings wherein like reference numbers generallyrepresent like parts of exemplary embodiments of the invention.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 sets forth a block diagram of a system configured for providingstorage array services first in the cloud then locally according toembodiments of the present invention.

FIG. 2 sets forth a block diagram of several example computers usefulfor providing cloud storage array services according first in the cloudthen locally according to embodiments of the present invention.

FIG. 3 sets forth a block diagram of an example storage controller of astorage array useful for locally providing cloud storage array services.

FIG. 4 sets forth an example block diagram of a system that locallyprovides cloud storage array services in accordance with embodiments ofthe present invention.

FIG. 5 sets forth a flow chart illustrating an exemplary method oflocally providing cloud storage array services according to embodimentsof the present invention

FIG. 6 sets forth a flow chart illustrating another method of locallyproviding cloud storage array services in accordance with embodiments ofthe present invention.

FIG. 7 sets forth a flow chart illustrating another method of locallyproviding cloud storage array services in accordance with embodiments ofthe present invention.

FIG. 8A depicts a computing environment that includes an implementationof an integrated storage manager in accordance with embodiments of thepresent invention.

FIG. 8B depicts a computing environment that includes an implementationof an integrated storage manager in accordance with embodiments of thepresent invention.

FIG. 9 sets forth a flow chart illustrating a method of locallyproviding cloud storage array services in accordance with embodiments ofthe present invention.

DETAILED DESCRIPTION OF EXEMPLARY EMBODIMENTS

Exemplary methods, apparatus, and products for providing cloud storagearray services for a storage array of a data center when the storagearray is not connected to a remote cloud-based storage array servicesprovider in accordance with the present invention are described withreference to the accompanying drawings, beginning with FIG. 1 . The term‘cloud’ as used in this specification refers to systems and computingenvironments that provide services to user devices through the sharingof computing resources through a network. Generally, the user device isunaware of the exact computing resources utilized by the cloud system toprovide the services. Although in many cases such ‘cloud’ environmentsor systems are accessible via the Internet, readers of skill in the artwill recognize that any system that abstracts the use of sharedresources to provide services to a user through any network may beconsidered a cloud-based system.

FIG. 1 sets forth a block diagram of a system configured for locallyproviding cloud storage array services according to embodiments of thepresent invention. The system of FIG. 1 includes a number of computingdevices (164, 166, 168, 170). Such computing devices may be implementedin a number of different ways. For example, a computing device may be aserver in a data center, a workstation, a personal computer, a notebook,or the like.

The computing devices (164-170) in the example of FIG. 1 are coupled fordata communications to a number of storage arrays (102, 104) through astorage area network (SAN) (158) as well as a local area network (160)(LAN). The SAN (158) may be implemented with a variety of datacommunications fabrics, devices, and protocols. Example fabrics for sucha SAN may include Fibre Channel, Ethernet, Infiniband, SAS (SerialAttached Small Computer System Interface), and the like. Example datacommunications protocols for use in such a SAN (158) may include ATA(Advanced Technology Attachment), Fibre Channel Protocol, SCSI, iSCSI,HyperSCSI, and others. Readers of skill in the art will recognize that aSAN is just one among many possible data communications couplings whichmay be implemented between a computing device and a storage array. Anyother such data communications coupling is well within the scope ofembodiments of the present invention.

The local area network (160) of FIG. 1 may also be implemented with avariety of fabrics and protocols. Examples of such fabrics includeEthernet (802.3), wireless (802.11), and the like. Examples of such datacommunications protocols include TCP (Transmission Control Protocol),UDP (User Datagram Protocol), IP (Internet Protocol), HTTP (HyperTextTransfer Protocol), WAP (Wireless Access Protocol), HDTP (HandheldDevice Transport Protocol), SIP (Session Initiation Protocol), RTP (RealTime Protocol) and others as will occur to those of skill in the art.

The example storage arrays (102, 104) of FIG. 1 provide persistent datastorage for the computing devices. Each storage array (102, 104)includes a storage controller (106, 112). The storage controller is amodule of automated computing machinery comprising computer hardware,computer software, or a combination of computer hardware and software.The storage controller may be configured to carry out variousstorage-related tasks. Such tasks may include writing data received froma computing device to storage, erasing data from storage, retrievingdata from storage to provide to a computing device, monitoring andreporting of disk utilization and performance, performing RAID(Redundant Array of Independent Drives) or RAID-like data redundancyoperations, compressing data, encrypting data, and so on.

Each storage controller (106, 112) may be implemented in a variety ofways, including as an FPGA (Field Programmable Gate Array), a PLC(Programmable Logic Chip), an ASIC (Application Specific IntegratedCircuit), or computing device that includes discrete components such asa central processing unit, computer memory, and various adapters. Eachstorage controller (106, 112) may, for example, include a datacommunications adapter configured to support communications via the SAN(158) and the LAN (160). For clarity, only one of the storagecontrollers (112) in the example of FIG. 1 is depicted as coupled to theLAN (160) for data communications. Readers should understand that bothstorage controllers (106, 112) are independently coupled to the LAN(160). Each storage controller (106, 112) may also, for example, includean I/O controller or the like that couples the storage controller (106,112) for data communications, through a midplane (114), to a number ofstorage devices (146, 150), and a number of write buffer (148, 152)devices.

Each write buffer device (148, 152) may be configured to receive, fromthe storage controller (106, 112), data to be stored in the storagedevices (146). Such data may originate from any one of the computingdevices (164-170). In the example of FIG. 1 , writing data to the writebuffer device may be carried out more quickly than writing data to thestorage device. The storage controller (106, 112) may be configured toeffectively utilize the write buffer devices (148, 152) as a quicklyaccessible redundant buffer for data destined to be written to storage.In this way, if the storage device to which the data is to be writtenfails or if the write does not complete, the write buffer device maymaintain the data to be written during a retry of the write or duringfailover of the storage device to another location. That is, the writebuffer device may provide redundancy for the storage devices.

A ‘storage device’ as the term is used in this specification refers toany device configured to record data persistently. The term‘persistently’ as used here refers to a device's ability to maintainrecorded data after loss of a power source. Examples of storage devicesmay include mechanical, spinning hard disk drives, Solid-state drives(“Flash drives”), and the like.

In addition to being coupled to the computing devices through the SAN(158), the storage arrays may also be coupled to the computing devicesthrough the LAN (160) and to one or more cloud service providers throughthe Internet (172). One example cloud service in FIG. 1 is a storagearray services provider (176). The storage array service provider (176)may be configured to provide various storage array services (184) suchas reporting of storage array performance characteristics, configurationcontrol of the storage arrays, and the like. The storage array servicesprovider may rely on modules executing on the storage array itself togather or process such data.

In some instances, the storage arrays (102, 104) may be disconnectedfrom the storage array services provider (176). Various reasons mayexist for such a disconnect. For example, a loss of data communicationsconnection between the storage array and the storage array servicesprovider (176) may occur. In high-security data centers, as anotherexample, the storage arrays (102, 104) may never be connected to thestorage array services provider at all. In such situations, users maystill desire the services provided by the storage array servicesprovider. To that end, the system of FIG. 1 may be configured, accordingto embodiments of the present invention, to locally provide cloudstorage array services for a storage array of a data center when thestorage array is not connected to a remote cloud-based storage arrayservices provider. Such local providing of the cloud storage arrayservices may be carried out by a storage array services module (182) ofone of the storage arrays (102, 104), referred to here as the ‘primary’storage array (180). The storage array services module (182) is a moduleof automated computing machinery comprising computer hardware, computersoftware, or a combination of computer hardware and software. Thestorage array services module (182) may locally provide the cloudstorage array services by, initiating one or more cloud storage arrayservices (184) and locally providing the cloud storage array services.Providing the cloud storage array services locally may includegenerating, by the cloud storage array services (184), metadatadescribing one or more real-time storage array characteristics andpresenting the metadata to a user through a local area network (160).‘Metadata’ as the term is used in this specification refers to data thatdescribes various characteristics of the storage array. Such data maytake on various forms in dependence upon the types of cloud storagearray services executing on the storage array. Some examples of suchservices may include a service that tracks and reports the rate and typeof access of the storage devices of the storage array, a service thattracks and reports throughput of the storage array, a service thatmonitors and reports memory wear leveling of the storage devices, aservice that reports capacity utilization of the storage devices, aservice that reports deduplication statistics, a service that reportsRAID (Redundant Array of Independent Drives) statistics, a service thatreports logical volume statistics, a service that monitors and reportspower consumption of the storage array, and other services as will occurto readers of skill in the art.

Prior to presentation, the metadata may be processed and analyzed. Suchanalysis processing and analysis may also be included in thepresentation of the metadata to the user through the LAN (160). That is,‘presenting the metadata’ is not limited to presenting the metadata inits original form. The metadata may be formatted, processed, analyzed,and otherwise altered for purposes of presentation.

As mentioned above, one example in which cloud storage array servicesare provided locally in accordance with embodiments of the presentinvention includes when a loss of data communications occurs. To thatend, the primary storage array (180), through the storage array servicesmodule (182) may be configured to detect a data communicationsconnection between the primary storage array (180) and a remotecloud-based storage array services provider (176). Here, a ‘heartbeat’signal may be used to ensure that the data communications connectionbetween the primary storage array (180) and the cloud-based storagearray services provider (176) is maintained. Such a ‘heartbeat’ may be aperiodic ping of the storage array services provider. As long as theping is returned, the storage array services module (182) may infer thatthe data communications connection between the storage array servicesprovider (176) and the primary storage array (180) has not been lost. Insuch an embodiment, the cloud-based storage array services provider(176) may provide the cloud storage array services remotely, rather thanthe storage array services module (182).

Further, while the data communications connection between the primarystorage array (180) and the storage array services provider (176) isactive, the storage array services module (182) may periodicallyretrieve, from the remote cloud-based storage array services provider(176), a current configuration of the cloud storage array services andthe current configuration of the plurality of storage arrays (102, 104)in the data center. The term ‘current configuration of the cloud storagearray services’ may include any data related to the execution of theservices including, for example, a list of the types of services to beexecuted, the executable computer program instructions of the servicesthemselves, updates to the executable computer program instructions ofthe services, data used to seed the services, data describing the formatof presenting the results of the services, and so on. The term ‘currentconfiguration of the plurality of storage arrays’ refers to any datadescribing each of the storage arrays of the data center including:storage capabilities of each storage array; data communicationscapabilities, endpoints, and present connectivity of each storage array;one or more identifiers of the storage array or the array's components;a listing of components of the storage array; an identification oflogical volumes maintained by the storage array; and the like. Byperiodically updating these current configurations, the storage arrayservices module (182) may be primed to locally provide the cloud storagearray services upon a loss of data communications between the primarystorage array (180) and the storage array services provider (176).

The storage array services module (182) may later detect loss of thedata communications connection between the primary storage array and theremote cloud-based storage array services provider. The storage arrayservices module (182) may detect such a loss of communications when apredefined number of pings of the heartbeat signal are not returned.Responsive to detecting the loss of communications between the primarystorage array (180) and the storage array services provider (176), thestorage array services provider may then initiate the cloud storagearray services (184).

In embodiments in which multiple storage arrays are included in the datacenter, each storage array may be independently coupled for datacommunications to the cloud-based storage array services provider (176).In such embodiments, each storage array is generally unaware of theother storage arrays at least for purposes of participating in storagearray services offered by the cloud-based storage array servicesprovider (176). In such an embodiment, the cloud-based storage arrayservices provider may expose a REST (Representational State Transition)API (Application Programming Interface), or the like, to the storagearrays to carry out data communications between a storage array serviceand a storage array. REST APIs generally utilize HTTP commands and adomain as the basis for data communications to between two endpoints. Tothat end, upon a loss of communications with the cloud-based storagearray services provider (176), the primary storage array (180) mayinitiate the one or more cloud storage array services (184) by alteringa local DNS (Domain Name Service) record such that the domain originallyutilized by the cloud-based storage array services provider (176)redirects to an IP address of the primary storage array. In this way,any communications that would normally be addressed to the cloud-basedstorage array services provider from any storage array in the datacenter are now redirected to the primary storage array (180).

In such an embodiment in which multiple storage arrays are locatedwithin a single data center, generating metadata describing one or morereal-time storage array characteristics may also include generatingmetadata describing one or more real-time storage array characteristicsof each of the plurality of the storage arrays; and aggregating, forpresentation to the user, the metadata of each of the plurality ofstorage arrays.

Although the example of FIG. 1 depicts the primary storage array (180)as the host of the cloud storage array services (184), other storagearrays may host the services in various circumstances. In this way,initiating the one or more cloud storage array services may also includeselecting, by the primary storage array through the storage arrayservices module (182) one of the plurality of storage arrays in the datacenter to host the one or more cloud storage array services independence upon workload characteristics of each of the plurality ofstorage arrays. The term ‘workload characteristics’ here refers to anymetric that may be utilized to infer availability of processingcapabilities. Examples of such workload characteristics may includeprocessing capabilities of each storage array (CPU speed, memory busspeed, and the like), a history of storage access operations over apredefined period of time, status of a job queue directed to accessing avolume hosted on a storage array, and so on as will occur to readers ofskill in the art. That is, a storage array with less workload than allother storage arrays may be utilized to host the cloud storage arrayservices (184) so that primary data storage operations are unaffected.

In embodiments in which workload characteristics are utilized to selecta host for the cloud-based storage array services, the primary storagearray (180) may also be configured to detect a change in workloadcharacteristics of each of the plurality of storage arrays. Such achange may be detected in a variety of ways including, for example, bydetecting a failure of a storage array, by periodically retrievingworkload characteristics, and so on. Upon detecting the change, theprimary storage array (180) may then re-select one of the storage arraysto host the one or more cloud storage array services in dependence uponthe changed workload characteristics. In this way, hosting of theservices may be dynamically reassigned when workload changes amongst thestorage arrays.

In embodiments in which a storage array other than the primary storagearray (180) is selected to host the cloud-based storage array services,the primary storage array may operate as a proxy for the selectedstorage array. In such an embodiment, presenting the metadata to a userthrough a local area network may include presenting the metadata throughthe proxy of the primary storage array. The primary storage array (180)may operate as a proxy in different ways. In one way, the primarystorage array receives only the final aggregated results forpresentation to the user through the local area network (160). That is,the selected storage array actually hosting the cloud-based storagearray services (184) may perform the services, collecting metadata fromall storage arrays, aggregate the metadata into a single result and passthat result on to the primary storage array for presentation to a user.In another example, the selected storage array may execute thecloud-based storage array services and each storage array may pass itsmetadata directly to the primary storage array. In such an embodiment,the primary storage array may aggregate and process the metadata of eachstorage array prior to presenting the aggregated and processed metadatato a user through the LAN (160).

The arrangement of computing devices, storage arrays, cloud-basedservice providers, networks and other devices making up the exemplarysystem illustrated in FIG. 1 are for explanation, not for limitation.Systems useful according to various embodiments of the present inventionmay include different configurations of servers, routers, switches,computing devices, and network architectures, not shown in FIG. 1 , aswill occur to those of skill in the art.

Locally providing cloud storage array services in accordance withembodiments of the present invention is generally implemented withcomputers. In the system of FIG. 1 , for example, all the computingdevices (164-170), storage arrays (102, 104), and storage array servicesprovider (176) may be implemented to some extent at least as computers.For further explanation, therefore, FIG. 2 sets forth a block diagramseveral example computers useful for locally providing cloud storagearray services according to embodiments of the present invention. Theexample computers in FIG. 2 include a primary storage array (202), aclient-side computer (204), and a storage array services provider (176).For clarity, only one computer, the primary storage array (202), in theexample of FIG. 2 is depicted with a number of various computingcomponents which are described below in greater detail. Readers willunderstand that the client-side user computer (204) and storage arrayservices provider (176) may include similar components that operate in asimilar manner.

The primary storage array (202) of FIG. 2 includes at least one computerprocessor (210) or ‘CPU’ as well as random access memory (214) (RAM′)which is connected through a high speed memory bus and bus adapter (212)to processor (210) and to other components of the primary storage array(202). Stored in RAM (214) is a storage array services module (182), amodule of computer program instructions that, when executed, causes theprimary storage array (202) of FIG. 2 to locally provide cloud storagearray services when the storage array (202) is not connected to a remotecloud-based storage array services provider (172) by initiating one ormore cloud storage array services (184) and locally providing the cloudstorage array services including: generating, by the cloud storage arrayservices, metadata (226) describing one or more real-time storage arraycharacteristics; and presenting the metadata to a user through a localarea network.

Here, the user may receive or view the metadata (226) through aclient-side array services module (228) stored in RAM (238) of aclient-side user computer (204). In the example of FIG. 2 , theclient-side user computer (204) is depicted as being coupled through theSAN (158) to the storage array (202) for use in storing data in thestorage array. Alternatively, the client-side user computer (204) may bea device that is not connected to the storage array (202) for purposesof storing data but rather may be connected only via a LAN for purposesof receiving results of the cloud storage array services. Consider, forexample, a client-side user computer that is implemented as a mobiledevice that is carried by a system administrator. Although the mobiledevice is not coupled to the storage array for purposes of data storage,the system administrator may utilize the mobile device to request andreceive results from various reporting services that indicate storagearray performance characteristics, errors, alerts, and the like.

In some embodiments, prior to the storage array services module (182)initiating cloud storage array services (184) locally, such cloudstorage array services may be provided remotely via the storage arrayservices provider (176). In such an embodiment, the cloud storage arrayservices (184) may be stored in RAM (24) of the storage array servicesprovider (176) and be accessible via an API exposed by the storage arrayservices provider via data communications over the Internet (172) orsome other wide-area network.

Turning back to the components of the primary storage array (202), alsostored in RAM (214) is an operating system (234). Examples of operatingsystems useful in primary storage arrays configured for locallyproviding cloud storage array services according to embodiments of thepresent invention include UNIX™, Linux, Microsoft Windows™, and othersas will occur to those of skill in the art. The operating system (234),the storage array services module (182), the cloud storage arrayservices (184) and the metadata (226) in the example of FIG. 2 are shownin RAM (168), but many components of such software typically are storedin non-volatile memory also, such as, for example, on a disk drive(224). Likewise, the modules depicted in RAM (238, 240) of theclient-side user computer (204) and the storage array services provider(176) may be stored in non-volatile memory.

The primary storage array (202) of FIG. 2 also includes disk driveadapter (222) coupled through an expansion bus and bus adapter (212) tothe processor (210) and other components of the primary storage array(202). Disk drive adapter (222) connects non-volatile data storage tothe primary storage array (202) in the form of disk drive (224). Diskdrive adapters may be implemented in a variety of ways including as SATA(Serial Advanced Technology Attachment) adapters, PATA (Parallel ATA)adapters, Integrated Drive Electronics (‘IDE’) adapters, Small ComputerSystem Interface (SCSI′) adapters, and others as will occur to those ofskill in the art. Non-volatile computer memory also may be implementedas an optical disk drive, electrically erasable programmable read-onlymemory (so-called ‘EEPROM’ or ‘Flash’ memory), RAM drives, and so on, aswill occur to those of skill in the art.

The example primary storage array (202) of FIG. 2 includes one or moreinput/output (′I/O′) adapters (216). I/O adapters implementuser-oriented input/output through, for example, software drivers andcomputer hardware for controlling output to display devices such ascomputer display screens, as well as user input from user input devices(220) such as keyboards and mice. The example primary storage array(202) of FIG. 2 also includes a video adapter (208), which is an exampleof an I/O adapter specially designed for graphic output to a displaydevice (206) such as a display screen or computer monitor. Video adapter(208) is connected to the processor (210) through a high speed videobus.

The exemplary primary storage array (202) of FIG. 2 includes acommunications adapter (218) for data communications with othercomputers (204, 176) through the Internet (172). Such datacommunications may be carried out through data communications networkssuch as IP data communications networks, and in other ways as will occurto those of skill in the art. Communications adapters implement thehardware level of data communications through which one computer sendsdata communications to another computer, directly or through a datacommunications network. Examples of such communications adapters usefulinclude modems for wired dial-up communications, Ethernet (IEEE 802.3)adapters for wired data communications, and 802.11 adapters for wirelessdata communications.

The example of FIG. 2 depicts a storage array implemented as one type ofexample computer. Readers of skill in the art will immediatelyrecognize, however, that such a storage array useful for locallyproviding cloud storage array services in accordance with embodiments ofthe present invention may be implemented in a variety of different waysand include a variety of different components. To that end and forfurther explanation, FIG. 3 sets forth a block diagram of an examplestorage controller (106) of a primary storage array (202) configured forlocally providing cloud storage array services in accordance withembodiments of the present invention. The example storage controllerincludes a computer processor (314). The computer processor is coupledto RAM (214) through a DDR4 (Double-Data Rate 4) bus. Stored in RAM(214) is a storage array services module (182) that operates asdescribed above to locally provide one or more cloud storage arrayservices (184) including the generation and presentation, to a user, ofmetadata (226) describing real-time storage array characteristics.

The processor (314) is also coupled for data communications through PCIe(Peripheral Component Interface express) links (308, 310, 312, 322) toseveral Fibre Channel host bus adapters (302, 304), an Ethernet adapter(306), and a PCIe switch (324). The Fibre Channel host bus adapters(308, 310) may couple the storage controller to a storage area network,such the SAN (158) depicted in the example of FIGS. 1 and 2 . TheEthernet adapter (306) may couple the storage controller to a local areanetwork such as the LAN (160) depicted in the example of FIGS. 1 and 2 .The PCIe switch (324) may provide data communications across other PCIlinks through the midplane to PCI endpoints, such as storage devices orwrite buffer devices. Likewise, the processor (314) is also coupledthrough a SAS (Serial Attached SCSI) host bus adapter (316) to a SASexpander (320). The SAS expander may provide SAS connections between thecomputer processor (314) and other devices through the midplane.

Readers of skill in the art will recognize that these components,protocols, adapters, and architectures are for illustration only, notlimitation. Such a storage controller may be implemented in a variety ofdifferent ways. Each such way is well within the scope of the presentinvention.

For further explanation, FIG. 5 sets forth a flow chart illustrating anexemplary method for locally providing cloud storage array servicesaccording to embodiments of the present invention. The method of FIG. 5includes initiating (402), by a primary storage array (202), one or morecloud storage array services (184). Initiating (402) one or more cloudstorage array services (184) may include deploying and executing one ormore modules of computer program instructions.

The method of FIG. 5 also includes locally providing (404) the cloudstorage array services (184). In the method of FIG. 5 , locallyproviding (404) the cloud storage array services (184) is carried out bygenerating (406), by the cloud storage array services (184), metadata(226) describing one or more real-time storage array characteristics;and presenting (408) the metadata to a user through a local areanetwork. Generating (406) such metadata may be carried out in variousways depending upon the type of service performed. In embodiments inwhich a service reports throughput of a storage array, the service maymonitor a number of data storage write operations completed over apredefined period time. Such a number is metadata describing real-timestorage array characteristic.

Presenting (408) metadata (226) locally to a user may be carried out bysending the data through the local area network (160) to a client-sidearray services module for presentation in a GUI (Graphical UserInterface) (410). A client-side array services module (228) is a moduleof automated computing machinery comprising computer hardware, computersoftware, or a combination of computer hardware and software that isconfigured to receive and present in a GUI metadata from cloud storagearray services. One example of a client-side array services module (228)may be a web browser and the GUI (410) may be a webpage hosted by theprimary storage array (202). In another example, the client-side arrayservices module (228) may be implemented as an application for a mobiledevice. These are but a few of many possible implementations of aclient-side array services module (228) that may be configured toreceive and present metadata to a user.

For further explanation, FIG. 5 sets forth a flow chart illustratinganother method of locally providing cloud storage array services inaccordance with embodiments of the present invention. The method of FIG.5 is similar to the method of FIG. 4 including, as it does: initiating(402) one or more cloud storage array services (184) and locallyproviding (404) the cloud storage array services including: generating(406) metadata; and presenting (408) the metadata to a user through alocal area network (160).

The method of FIG. 5 differs from the method of FIG. 5 , however, inthat the method of FIG. 5 also includes detecting (502), by the primarystorage array (202) prior to initiating (402) the cloud storage arrayservices (184), a data communications connection (512) between theprimary storage array (202) and a remote cloud-based storage arrayservices provider (176). Detecting (502) a data communicationsconnection (512) between the primary storage array (202) and the remotecloud-based storage array services provider (176) may be carried out ina variety of manners. In one example, the primary storage array (202)may periodically ping the cloud-based storage array services provider(176). Each ping is returned by the cloud-based storage array servicesprovider as long as a data communications connection over the wide areanetwork (WAN) (512) is active.

While the data communications connection is active, the method of FIG. 5includes providing (506), by the remote cloud-based storage arrayservices provider (176), the cloud storage array services. Thecloud-based storage array services provider (176) may provide manydifferent types of cloud storage array services (184) in many differentways. In one example, the cloud-based storage array services provider(176) may expose an API to the primary storage array (and other storagearrays) where the API enables the performance of the cloud storage arrayservices.

Also while the data communications connection between the primarystorage array (202) and the remote cloud based storage array servicesprovider (176) is active, the method of FIG. 5 may optionally includeperiodically retrieving (504), by the primary storage array from theremote cloud-based storage array services provider, a currentconfiguration (508) of the cloud storage array services and a currentconfiguration (508) of the plurality of storage arrays. Theconfiguration of cloud storage array services may be updated over timeby developers of the cloud storage array services and the configurationof the storage arrays in the data center may updated by systemadministrators of the storage arrays or data center.

The method of FIG. 5 also includes detecting (508), by the primarystorage array (202), loss of the data communications connection (514)between the primary storage array (202) and the remote cloud-basedstorage array services provider (176). Continuing with the heartbeatexample described above, upon a predefined number of un-returned pings,the primary storage array (202) may infer a loss of data communicationsconnection between the primary storage array (202) and the cloud-basedstorage area service provider (176). In an embodiment in which a datacommunication connection was previous active then is lost, the primarystorage array (202) may be configured to initiate (402) the one or morecloud storage array services by the primary storage array only inresponse to detecting the loss of the data communications connectionbetween the primary storage array and the remote, cloud-based storagearray services provider.

For further explanation, FIG. 6 sets forth a flow chart illustratinganother method of locally providing cloud storage array services inaccordance with embodiments of the present invention. The method of FIG.6 is similar to the method of FIG. 4 including, as it does: initiating(402) one or more cloud storage array services (184) and locallyproviding (404) the cloud storage array services including: generating(406) metadata; and presenting (408) the metadata to a user through alocal area network (160).

The method of FIG. 6 differs from the method of FIG. 5 , however, inthat in the method of FIG. 6 , the data center includes a plurality ofstorage arrays (602, 604), including the primary storage array (202).Also in the method of FIG. 5 generating (406) metadata (226) describingone or more real-time storage array characteristics includes: generating(606) metadata describing one or more real-time storage arraycharacteristics of each of the plurality of the storage arrays (602,604, 402) and aggregating (608), for presentation to the user, themetadata (226) of each of the plurality of storage arrays. In this way,cloud storage array services may be performed for a plurality of storagearrays in a single data center and all results are aggregated forpresentation of a user.

For further explanation, FIG. 7 sets forth a flow chart illustratinganother method of locally providing cloud storage array services inaccordance with embodiments of the present invention. The method of FIG.7 is similar to the method of FIG. 4 including, as it does: initiating(402) one or more cloud storage array services (184) and locallyproviding (404) the cloud storage array services including: generating(406) metadata; and presenting (408) the metadata to a user through alocal area network (160).

The method of FIG. 6 differs from the method of FIG. 5 , however, inthat in the method of FIG. 6 , the data center includes a plurality ofstorage arrays (702, 704), including the primary storage array (202).The method of FIG. 7 differs from the method of FIG. 5 in that in themethod of FIG. 7 initiating (402), by the primary storage array, one ormore cloud storage array services (402) includes selecting (706), by theprimary storage array (202) in dependence upon workload characteristicsof each of the plurality of storage arrays (702, 704), one of theplurality of storage arrays to host the one or more cloud storage arrayservices (184). Selecting a storage array to host the cloud storagearray services in dependence upon workload characteristics may includeretrieving from each of the storage arrays one or more metrics usefulfor inferring availability of processing capabilities and selecting thestorage array with the greatest inferred availability of processingcapabilities.

The method of FIG. 7 also includes detecting (708), by the primarystorage array (202), a change in workload characteristics of each of theplurality of storage arrays and re-selecting (710) one of the pluralityof storage arrays to host the one or more cloud storage array servicesin dependence upon the changed workload characteristics. The primarystorage array (202) may be configured to periodically request workloadcharacteristics from each of the plurality of storage arrays anddetermine if a change in the workload characteristics necessitates achange in selection of the storage array hosting the cloud storage arrayservices (184).

The method of FIG. 7 also includes operating (714), by the primarystorage array (202), as a proxy for the selected storage array (716)when the selected storage array (716) is not the primary storage array(202). Operating (714) as a proxy may take various forms. As mentionedabove, the primary storage array (202) may operate as a proxy byreceiving a final aggregated result of the performance of the cloudstorage array services or may operate as a proxy by receiving, from eachstorage array independently, metadata streams generated as a result ofthe execution of the cloud storage array services by the selectedstorage array (716). In the latter example, the primary storage array(202) may process, analyze, and aggregated the various independentstreams of metadata. To that end, presenting (408) the metadata to auser through a local area network in the method of FIG. 7 is carried outby presenting (712) the metadata through the proxy of the primarystorage array (714).

For further explanation, FIG. 8A illustrates an example computingenvironment for an integrated storage manager (800) operating between aplurality of storage systems and multiple container orchestrators—wherethe integrated storage manager (800) is implemented as part of the cloudstorage array services (184) of a storage array services module (182)that locally provides cloud storage array services to one or more clientcomputing devices.

In this example, a “storage system” may be considered to be a “storagearray” as described above with reference to FIGS. 1-7 , where a storagesystem (802A-802N) may be implemented similarly or equivalently to thestorage arrays (102, 202).

In some implementations, the locally provides cloud storage services areprovided in response to unavailability of remote cloud storage services,such as remote storage array services providers (176). However, in otherexamples, the locally provided cloud storage services (184) are providedwhether or not the local plurality of storage systems are connected to aremote services provider.

As depicted within FIG. 8 , a client computing device (802) may includea client-side array services module (228), such as described above withregard to FIGS. 1-7 . Further, the client computing device (802) requestand receive cloud storage array services (184)—where the cloud storagearray services (184) may be implemented by a storage array servicesmodule (182) operating within one or more of the storage systems(802A-802N).

In some cases, the cloud storage array services (184) may be implementedwithin a storage array services module (182) that is a computing device(not depicted) other than the storage systems (802A-802N), where thecomputing device is on the same local network as the client computingdevice(s) (802) and the storage systems (802A-802N). In someimplementations, as described above, any of the storage systems(802A-802N) may serve as the primary storage array (202).

Further, the cloud storage array services (184) may includevirtualization services and/or operating system level virtualizationservices such as a containerization service (808), a hybrid cloudcontainer orchestration (814), and/or a container orchestration system(820).

In some implementations, an integrated storage manager (800) may be incommunication, across one or more networks (not depicted), with thestorage systems (800A-800N) and with multiple different virtualizationservices, including services that provide operating system levelvirtualization, or containers—including containerization service (808),such as Docker™, hybrid cloud container orchestration (814), such asMesosphere™, and Container Orchestration Service (820), such asKubernetes™. In other examples, the integrated storage manager (800) maybe in communication with other container service providers. Further, inthis example, containerization service (808) may include multipleimplementations of containers, including container(s) (810), whichincludes a plugin (812) for interfacing with the integrated storagemanager (800), for example, via an API; hybrid cloud containerorchestration (814) may include multiple implementations of containers,including container(s) (816), which includes a plugin (818) forinterfacing with the integrated storage manager (800); and containerorchestration system (820) may include a provisioner (822) and a plugin(824).

In some implementations, each of the storage systems (802A-802N) mayinclude respective API interfaces (804), where the API interface (804)may be used for communicating with the integrated storage manager (800).

For further explanation, FIG. 8B illustrates an implementation ofmultiple components of an integrated storage manager (800). In thisexample, the integrated storage manager (800) may include multiplemodules, including provisioner (830), data protector (832), attacher(484), statistics (836), mounter (838), and enumerator (840). In thisexample, provisioner (830) may provision storage system resources fromamong the connected storage systems, data protector (832) may implementone or more data security protocols, attacher (834) may attach or detachvolumes within the containers or within the storage systems, statistics(836) may aggregate and calculate various performance metrics and datastorage usage parameters and characteristics, mounter (838) may mount orunmount volumes within the containers or within the storage systems, andenumerator (840) may generate metadata for tracking or searching fordata volumes, snapshots, or other data objects stored among the storagesystems and containers.

For further explanation, FIG. 9 sets forth a flow chart illustrating anexample method for an integrated storage manager (800) according to someembodiments of the present disclosure. Although depicted in less detail,the example integrated storage manager (800) may be similar to theintegrated storage managers described above with reference to FIG. 8A or8B, or any combination thereof.

In this example, the cloud storage array services (184) may locallyprovide the cloud storage services (404)—where the local cloud storageservices (404) may include an integrated storage manager (800)configured to: receive (902), from one or more storage systems fromamong a plurality of storage systems (802A-802N), one or moreperformance analyses (954); receive (904) a management request (952)from an operating system level virtualization service (808); anddetermine (906), among the plurality of storage systems (802A-802N), animplementation of the request (952) from the operating system levelvirtualization service (808).

Receiving (902), from one or more storage systems from among a pluralityof storage systems (802A-802N), one or more performance analyses (954)may be implemented by a storage system (802A-802N) sending metrics, suchas performance metrics for the storage system, or an analysis ofworkload performance, across a network using API interface (804) tocommunicate with the API interface on the integrated storage manager(800).

Receiving (904) a request (952) from an operating system levelvirtualization service (808) may be implemented by the integratedstorage manager (800) receiving one or more messages across a localnetwork, local mesh fabric, or via a direct connection using one or morenetwork communication protocols.

Determining (906), among the plurality of storage systems, animplementation of the request from the operating system levelvirtualization service (808) may be implemented by applying a selectionpolicy to select one or more storage systems to provide storage and/orcomputing resources for implementing the request (952). In someexamples, the selection policy may be configured to satisfy one or moreof: balancing workload distributions across the plurality of storagesystems (802A-802N), balancing data storage consumption across theplurality of storage systems (802A-802N), or satisfying one or morequality of service terms for a given client.

Further, in some implementations, determining (906) an implementationfor the request (952) may include determining (908), based at least uponthe one or more performance analyses (554) for the one or more storagesystems, an implementation of the management request that is modified toimprove one or more metrics corresponding to the one or more storagesystems may be implemented by the integrated storage manager (800)determining multiple versions of a performance impact among the one ormore storage systems based on implementing the management request inmultiple ways, where the multiple ways include an implementation, suchas provisioning, based on a performance analysis indicating a particularbalance of workloads—where the determination, in this example, may bemade to improve a performance balance of workloads among the one or morestorage systems given a provisioning of data storage for a new workloadamong the one or more storage systems. For example, if the integratedstorage manager (800) determines a particular one or more storagesystems will be less lightly used, then those particular one or morestorage systems may be selected for implementing the management request.

In other examples, the integrated storage manager (800) may beimplemented to service bare metal applications as well as virtualizedapplications. In other examples, the integrated storage manager (800)may communicate with a management application for one or more storageservices, such as a management application that runs in a cloudenvironment that manages the one or more storage systems (802A-802N). Inother examples, the integrated storage manager (800) may receiveanalytics data from one or more containers, or Kubernetes pods orclusters at different granularities.

Further, in some examples, the integrated storage manager (800) mayimplement an agent (not depicted) within a host computer or some othercomputing device that is in communication with the one or more storagesystems or containers, where the agent may provide an interface to oneor more of the services provided by the integrated storage manager(800), including provisioning volumes or data, and mounting orunmounting volumes, and more generally for providing a host-sideinterface for each of the modules depicted in FIG. 8B. In some examples,the integrated storage manager (800) may provide information to thecontainerization service (808), the hybrid cloud container orchestration(814), and/or the container orchestration system (820), and/or thestorage systems (802A-802N), where the recipients may use theinformation for scheduling workloads or data storage operations,balancing workloads, or other management functions for managing datastorage.

Generating (910) metadata (926) describing one or more results from theimplementation of the request (954) may be implemented similarly togenerating (406) metadata describing one or more real-time storage arraycharacteristics, as discussed above with reference to FIG. 4 , where themetadata (926) may enable a GUI on a client device to provideinformation regarding success or failure, state changes, and/orconsequences or effects of the implementation.

Providing (912) the metadata (926) through a local area network (160)may be implemented similarly to presenting (408) the metadata (226) to auser through a local area network, as discussed above with reference toFIG. 4 .

Exemplary embodiments of the present invention are described largely inthe context of a fully functional computer system. Readers of skill inthe art will recognize, however, that the present invention also may beembodied in a computer program product disposed upon computer readablemedia for use with any suitable data processing system. Such computerreadable storage media may be any transitory or non-transitory media.Examples of such media include storage media for machine-readableinformation, including magnetic media, optical media, or other suitablemedia. Examples of such media also include magnetic disks in hard drivesor diskettes, compact disks for optical drives, magnetic tape, andothers as will occur to those of skill in the art. Persons skilled inthe art will immediately recognize that any computer system havingsuitable programming means will be capable of executing the steps of themethod of the invention as embodied in a computer program product.Persons skilled in the art will recognize also that, although some ofthe exemplary embodiments described in this specification are orientedto software installed and executing on computer hardware, nevertheless,alternative embodiments implemented as firmware, as hardware, or as anaggregation of hardware and software are well within the scope ofembodiments of the present invention.

It will be understood from the foregoing description that modificationsand changes may be made in various embodiments of the present inventionwithout departing from its true spirit. The descriptions in thisspecification are for purposes of illustration only and are not to beconstrued in a limiting sense. The scope of the present invention islimited only by the language of the following claims.

What is claimed is:
 1. A method comprising: receiving a request for storage resources from an operating system level virtualization service; determining, among the plurality of storage systems, an implementation of the request from the operating system level virtualization service; and providing storage resources to the operating system level virtualization service in accordance with the implementation of the request from the operating system level virtualization service based on aggregated performance metrics and data storage usage characteristics associated with one or more storage systems that are utilized to provide the storage resources.
 2. The method of claim 1 wherein the request for storage resources includes a request for one or more volumes that can be utilized by the operating system level virtualization service.
 3. The method of claim 1 wherein the request for storage resources includes a request to implement one or more data security protocols for communications between the operating system level virtualization service and the storage resources.
 4. The method of claim 1 wherein the storage resources are provided to the operating system level virtualization service in dependence upon aggregated performance metrics and data storage usage characteristics associated with one or more storage systems that are utilized to provide the storage resources.
 5. The method of claim 4 further comprising receiving, from the one or more storage systems from among the plurality of storage systems, one or more performance analyses.
 6. The method of claim 5 wherein providing storage resources to the operating system level virtualization service comprises: determining, based at least upon the one or more performance analyses for the one or more storage systems, an implementation of the request that is modified to improve one or more metrics corresponding to the one or more performance analyses.
 7. The method of claim 1 wherein providing the storage resources to the operating system level virtualization service further comprises providing, by a primary storage system among the plurality of storage systems, the storage resources.
 8. The method of claim 1 further comprising: generating metadata describing one or more results from the implementation of the request from the operating system level virtualization service; and presenting the metadata to a client computing device through a local area network.
 9. The method of claim 8, wherein a data center further comprises the plurality of storage systems, including a primary storage system, and generating, by the cloud storage array services, metadata describing one or more real-time storage system characteristics further comprises: generating metadata describing one or more real-time storage system characteristics of each of the plurality of the storage systems; and aggregating the metadata of each of the plurality of storage systems.
 10. The method of claim 1, wherein the plurality of storage systems include a primary storage system, and wherein providing the storage resources to the operating system level virtualization service further comprises: selecting, by the primary storage system in dependence upon workload characteristics of each of the plurality of storage systems, one of the plurality of storage systems to provide the storage resources to the operating system level virtualization service.
 11. The method of claim 10, further comprising: detecting, by the primary storage system, a change in workload characteristics of each of the plurality of storage systems; and re-selecting one of the plurality of storage systems to provide the storage resources to the operating system level virtualization service in dependence upon the changed workload characteristics.
 12. The method of claim 10, further comprising operating, by the primary storage system, as a proxy for the selected storage system when the selected storage system is not the primary storage system.
 13. An apparatus comprising a computer processor and a computer memory operatively coupled to the computer processor, where the computer memory includes computer program instructions that, when executed by the computer processor, cause the apparatus to carry out the steps of: receiving a request for storage resources from an operating system level virtualization service; determining, among the plurality of storage systems; an implementation of the request from the operating system level virtualization service; and providing storage resources to the operating system level virtualization service in accordance with the implementation of the request from the operating system level virtualization service based on aggregated performance metrics and data storage usage characteristics associated with one or more storage systems that are utilized to provide the storage resources.
 14. The apparatus of claim 13 wherein the storage resources are provided to the operating system level virtualization service in dependence upon aggregated performance metrics and data storage usage characteristics associated with one or more storage systems that are utilized to provide the storage resources.
 15. The apparatus of claim 14, further comprising computer program instructions that, when executed by the computer processor, cause the apparatus to carry out the step of receiving, from the one or more storage systems from among the plurality of storage systems, one or more performance analyses.
 16. The apparatus of claim 15 wherein providing storage resources to the operating system level virtualization service comprises: determining, based at least upon the one or more performance analyses for the one or more storage systems, an implementation of the request that is modified to improve one or more metrics corresponding to the one or more performance analyses.
 17. The apparatus of claim 13 wherein providing the storage resources to the operating system level virtualization service further comprises: selecting, in dependence upon workload characteristics of each of the plurality of storage systems, one of the plurality of storage systems to provide the storage resources to the operating system level virtualization service.
 18. The apparatus of claim 17, further comprising computer program instructions that, when executed by the computer processor, cause the apparatus to carry out the steps of: detecting, by the primary storage system, a change in workload characteristics of each of the plurality of storage systems; and re-selecting one of the plurality of storage systems to provide the storage resources to the operating system level virtualization service in dependence upon the changed workload characteristics.
 19. A computer program product disposed upon a computer readable medium, the computer program product comprising computer program instructions that, when executed, cause a computer to carry out the steps of: receiving a request for storage resources from an operating system level virtualization service; determining, among the plurality of storage systems; an implementation of the request from the operating system level virtualization service; and providing storage resources to the operating system level virtualization service in accordance with the implementation of the request from the operating system level virtualization service based on aggregated performance metrics and data storage usage characteristics associated with one or more storage systems that are utilized to provide the storage resources.
 20. The computer program product of claim 19 wherein the storage resources are provided to the operating system level virtualization service in dependence upon aggregated performance metrics and data storage usage characteristics associated with one or more storage systems that are utilized to provide the storage resources. 